Update actions/labeler action to v6#97
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
❌ Deploy Preview for halo-universe failed. Why did it fail? →
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
renovate
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4→v6Release Notes
actions/labeler (actions/labeler)
v6.0.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/labeler@v6.0.0...v6.0.1
v6Compare Source
v6.0.0Compare Source
What's Changed
Breaking Changes
Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. Release Notes
Dependency Upgrades
Documentation changes
pull_request_targetto README.md by @silverwind in #669pull_request_targetevent by @IvanZosimov in #721New Contributors
Full Changelog: actions/labeler@v5...v6.0.0
v5Compare Source
v5.0.0Compare Source
What's Changed
This release contains the following breaking changes:
The ability to apply labels based on the names of base and/or head branches was added (#186 and #54). The match object for changed files was expanded with new combinations in order to make it more intuitive and flexible (#423 and #101). As a result, the configuration file structure was significantly redesigned and is not compatible with the structure of the previous version. Please read the action documentation to find out how to adapt your configuration files for use with the new action version.
The bug related to the
sync-labelsinput was fixed (#112). Now the input value is read correctly.By default,
dotinput is set totrue. Now, paths starting with a dot (e.g..github) are matched by default.Version 5 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20.
For more information, please read the action documentation.
New Contributors
Full Changelog: actions/labeler@v4...v5.0.0
v4.3.0Compare Source
What's Changed
In scope of this release, the ability to specify pull request number(s) was added by @credfeto in #349.
Support for reading from the configuration file presented on the runner was added by @lrstanley in #394. It allows you to use a configuration file generated during workflow run or uploaded from a separate repository.
Please refer to the action documentation for more information.
This release also includes the following changes:
New Contributors
Full Changelog: actions/labeler@v4...v4.3.0
v4.2.0Compare Source
What's Changed
In the scope of this release, the following outputs were added by @danielsht86 in #60:
new-labels- a comma-separated string that contains all newly added labels.all-labels- a comma-separated string that contains all labels currently assigned to the PR.For detailed information, please refer to our updated documentation.
The issue of encountering an
HttpError: Server Errorwhen adding more than 50 labels has been successfully resolved by @markmssd in #497. However, it's important to note that the GitHub API imposes a limit of 100 labels. To ensure smooth operation, a warning message that will alert you if the number of labels exceeds this limit was implemented. From this point forward, if more than 100 labels are specified, only the first 100 will be assigned.The error handling for the
Resource not accessible by integrationerror was added by @jsoref in #405. Now, if the workflow is misconfigured, the labeler provides a clear warning and guidance for correction.This release also includes the following changes:
New Contributors
Full Changelog: actions/labeler@v4...v4.2.0
v4.1.0Compare Source
What's Changed
In scope of this release, the
dotinput was added by @kachkaev in #316. It allows patterns to match paths starting with a period. This input is set tofalseby default.Usage
This release also includes the following changes:
New Contributors
Full Changelog: actions/labeler@v4...v4.1.0
v4.0.4Compare Source
What's Changed
New Contributors
Full Changelog: actions/labeler@v4...v4.0.4
v4.0.3Compare Source
What's Changed
repo-tokeninput optional. Default isgithub.token(#227)v4.0.2Compare Source
v4.0.1Compare Source
@actions/coredependency tov1.9.1to pull in recent security fixesConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.